tikv: check lock timeout again after resolving lock (#14066) #14083
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Yilin Chen [email protected]
What problem does this PR solve?
Fix #14063
What is changed and how it works?
Before resolving locks, we checked whether the locks are expired according to its own TTL. However, it's not accurate because heartbeat only updates the TTL of the primary key.
So we still fetch msBeforeTxnExpired from ResolveLocks. If msBeforeTxnExpired is not zero, it means there are still locks blocking us acquiring the pessimistic lock. We should return timeout error if necessary.
Check List
Tests
Code changes
Release note